Mobile device implemented payment functionality based on semantic analysis

ABSTRACT

Provide herein is a method and system capable of authenticating transactions involving at least one service provider and one or more users who are each in electronic communication. This electronic communication can be, for example, SMS, MMS, e-mail, or online account messaging. It is an aspect of certain embodiments where the transaction is an authentication and/or verification of an entity. Examples of such entities are products, actions and users.

This application is a Continuation of U.S. patent application Ser. No. 14/721,873, filed May 26, 2015, which is a continuation of U.S. application Ser. No. 13/074,037, filed Mar. 29, 2011, now U.S. Pat. No. 9,406,062, which is a Continuation-in-Part of application Ser. No. 10/734,352, filed Dec. 11, 2003, now U.S. Pat. No. 9,313,161, which is a Continuation of application Ser. No. 10/227,194, filed Aug. 21, 2002 (now U.S. Pat. No. 7,406,429), U.S. application Ser. No. 13/074,037 also claims the benefit of priority to Provisional Application No. 61/318,648, filed Mar. 29, 2010. The disclosures set forth in the referenced applications are incorporated herein by reference in their entireties.

FIELD OF THE INVENTION

The present invention relates to telecommunications. In particular, the invention relates to a method and system for authentication and/or verification via telecommunications.

BACKGROUND OF THE INVENTION

Services that are booked or used via the Internet are constantly increasing. The Internet enables one to use several on-line services such as services connected to banks, health services, travel agencies, vehicle maintenance, and so on.

The increasing popularity of mobile computing and communications devices introduce new challenges to services on the Internet. Mobile terminals are able to deliver information to users when needed and where needed. Users want ubiquitous access to information and applications from the device at hand. They also want to access and update this information wherever they happen to be.

It is important to notice, however, that not all the terminals will be mobile. Future services must be able to communicate with a large variety of terminal devices, both those that are mobile and those that are not. Different terminal devices have very different capabilities.

The interoperability of different services and terminal devices requires standards on several levels. It is not enough to have, say, common communication protocols. It would be very important to share common concepts and understanding what a certain piece of data means in a certain context. However, it has been very difficult to agree on those issues, as there exist an enormous number of companies, organizations, and other actors in the field.

Many services must be able to manage bookings. They include for example booking appointments for health services; booking travel reservations for hotels, airlines, and rental cars; booking tickets for venues; booking appointments for vehicle maintenance; booking maintenance for apartments; and so on. It would be very useful, if those services could get information from one another. For example, if a customer is booking tickets for a concert, he or she might want to book a table in a restaurant also. It helps, if the restaurant's booking service gets basic information, like date and customer's name from the theater's booking system. Unfortunately, there have not been methods to exchange information between different kinds of booking systems.

Additionally, such services as well as other services/companies such as banks and credit card companies have long had the problem of verifying that the user attempting to make a reservation, booking or purchase is the actual user that they claim to be. Similarly, customers would like to know that the information that they are providing to these services/companies is going to the actual company and that their information is secure. With identity fraud resulting from submitting personal information over the internet being a concern for many web users there exists the need for a safer authentication alternative than currently exists.

Companies and organizations, such as software developers and pharmaceutical companies, have for a long time dealt with the problem of piracy. Not only are such entities harmed by lost sales from counterfeit goods but consumers who unknowingly purchase counterfeit goods can be harmed by, for example, malware installed by hacked software or poor quality and mislabeled counterfeit drugs. Currently, such companies are trying to develop methods in which the authenticity of their products can be easily determined by their customers either prior to purchase or prior to use.

For services such as booking or calendar functions, information exchange often takes place as synchronizing booking or calendar entries. For that purpose, several important standardization efforts are going on. For example, SyncML is an industry initiative to develop and promote a single, common data synchronization protocol. vCalendar is an exchange format for personal scheduling information. It is applicable to a wide variety of calendaring and scheduling products and is useful in exchanging information across a broad range of transport methods. A number of vendors have adopted the specification because it allows their products to exchange calendaring and scheduling information. vCalendar is an open specification based on industry standards such as the x/Open and XAPIA Calendaring and Scheduling API (CSA), the ISO 8601 international date and time standard and the related MIME email standards. The vCalendar format utilizes data normally stored within a calendaring and scheduling application, facilitating the cross platform exchange of information about items such as events and to-do's. An event is a calendaring and scheduling entity that represents a designated amount of time on a calendar. A to-do is a calendaring and scheduling entity that represents an action item or assignment. For instance, it may be an item of work assigned to an individual.

vCard automates the exchange of personal information typically found on a traditional business card. vCard is used in applications such as Internet mail, voice mail, Web browsers, telephony applications, call centers, video conferencing, PIMs (Personal Information Managers), PDAs (Personal Data Assistants), pagers, fax, office equipment, and smart cards. In addition to text, vCard information may include elements like pictures, company logos, live Web addresses, and so on.

A common problem with all of these existing solutions is that they do not provide common semantics for different systems and the transfer of information may not always be as secure, or at least perceived as secure by customers, as many customers wish. Another problem is that booking systems have multiple different and usually quite complex user interfaces. If a customer wants to both make an appointment with a dentist and book a taxi to take him or her there, the customer needs to enter all the booking information to both booking systems in different ways. While the dentist may have in place a secure method of making reservations, authenticating the client who makes the reservation and receiving payment for a booking, the taxi company may not.

Additionally, it becomes challenging to manage client replies for instance when a client has been given a number of questions. For example, it makes sense to use SMS text messages to ask a client which option he or she chooses, because in many countries, like in Finland, it is very common to communicate with SMS text messages and they create revenues to operators. However, if a client replies to several inquires by sending a number of text messages, it can be troublesome to find out, which answer corresponds to a certain question because the reply does not automatically include a reference to the question. Say, a service asks a client if he or she wants to reserve—in addition to a flight ticket—also a taxi and a hotel room, and the client replies “yes” to one question but “no” to the other, the service does not necessarily know which offer the client has accepted.

Other problems, such as clients not showing up for appointments, not using a service more than once or long intervals between use of a service can be addressed through the use of new systems and methods.

SUMMARY OF THE INVENTION

The object of the invention is to provide a method and system capable of authenticating transactions involving at least one service provider and one or more users who are each communicating electronically.

It is an aspect of certain embodiments to provide a method and system capable of making booking type transactions between a plurality of service providers and a plurality of users who are each communicating with a mobile telephone capable of receiving and sending short text messages (e.g., SMS messages).

It is a further aspect of certain embodiments where the transaction is an authentication and/or verification of an entity. Examples of such entities are products, actions and users.

It is yet a further aspect of certain embodiments for the method and system to be used to augment a transaction for the benefit of the service provider. For instance, when a software developer releases a free trial version of a product to a plurality of users they often expect around 3% of those downloads to turn in to actual sales of the product. Through implementations of the embodiments of the present invention, the service provider can utilize SMS communication with the users who downloaded the trial to entice use and purchase of the paid program.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following section, the invention will be described in detail by the aid of a few examples of its embodiments, in which

FIG. 1 represents one advantageous system in accordance with an embodiment of the invention;

FIG. 2 represents a second advantageous system in accordance with an embodiment of the invention;

FIG. 3 represents a third advantageous system in accordance with an embodiment of the invention;

FIG. 4 is one advantageous example of a sequence diagram representing messages transmitted within a system in accordance with an embodiment of the invention;

FIG. 5 is a second advantageous example of a sequence diagram representing messages transmitted within a system in accordance with an embodiment of the invention.

FIG. 6 shows an example of the dynamic dialog matrix applied to a query and reply according to an embodiment of the invention.

FIG. 7 shows the phases of the booking process in an embodiment of the invention.

FIG. 8 shows a matrix diagram corresponding to Example 2, according to an embodiment of the invention.

DESCRIPTION OF THE INVENTION

Certain embodiments of the present invention relate to exchanging and synchronizing information between booking systems and user terminal devices. The services may be for example booking appointments for health services; booking travel reservations for hotels, airlines, and rental cars; booking tickets for venues; booking appointments for vehicle maintenance; booking maintenance for apartments; and so on.

The booking system in accordance with embodiments of the present invention comprises at least one service provider booking system; at least one service provider; a mediator; a client; at least one client terminal device that can be a mobile device capable of receiving text messages, and that includes a dialogue; and telecommunication connections that are used to connect the service provider booking systems, the service providers, the mediator and the client terminal device to one another.

The service providers are those with whom clients want to make appointments, reservations, or other bookings and comprise the resources for the booking system to allocate. Service providers conduct business through service provider booking services. As used in this application, the mediator is a network based service available to the service provider booking services over the network that provides additional semantics, translation and synchronization services needed for communication of the information needed for a client to complete a transaction with a service provider. The service provider booking services and the mediator are preferably applications operating on network servers such as the Internet or a private Intranet. In general, a system will comprise a plurality of service providers and service provider booking systems (implementing service provider booking services), but it is possible to have a simple booking system for only one service provider in which case the mediator and service provider could be tightly integrated into a single application.

Clients preferably include clients communicating on mobile telephones capable of receiving short text messages, such as Short Message Service (SMS) messages. Of course, a system that is capable of handling SMS messages will also handle other clients with greater capabilities. The mediator preferably communicates with mobile telephone clients through an SMS gateway, such as are operated by mobile telephone providers and a well known today. The mediator communicates with clients using dialogues. Dialogues are short messages which present information to the client and allow a simple reply. Dialogues preferably provide users with simple choices such as yes/no or to allow a selection from an ordered list. Dialogues can also be one way, such as to acknowledge a reservation. A transaction may typically involve a sequence of dialogues each involving a simple response. Dialogues involve asynchronous communication by messages. The system as described makes it possible to coordinate bookings among different service provider systems in order to fill a clients need, for example coordination of an airline booking with transportation to the airport.

FIG. 1 is a diagram of the simplest system comprising a single service provider booking system 100 for a single service provider, a mediator 102 communicating with the service provider over a network, and a user with a mobile phone having a dialogue entered thereon.

FIG. 2 shows a plurality of service provider booking systems communicating with a mediator over a network.

FIG. 3 shows a mediator named BookIT communicating with various service provider systems and users with telephone devices communicating dialogues.

A reason based customer dialogue is a desirable improvement from the client's point of view, because service providers can create their own dialogues in connection with each booking event. A dialogue is closely related to a certain booking situation. It becomes active automatically at the right moment, or the client can activate the dialogue as needed, or another entity in the system can send a message to the dialogue to activate it. The dialogue then sends an inquiry to another entity in the system or informs the client and possibly inquires client's choices. By means of this kind of dialogue, the client can make reservations in several booking systems using only one user interface. The dialogue connects to remote booking systems e.g. through the Internet or even mobile networks.

A mediator service can be capable of transmitting booking information between service provider booking systems. For example, after a booking is entered into an airline booking system, a taxi booking system can offer the client a lift to the airport. In this application, a booking is an allocation of a single resource (either the airline booking or the taxi in the previous example), while a reservation is the union of the bookings for all of the resources for the same event (the airline booking plus the taxi booking in the previous example). The dialogue between the client, the mediator and the booking systems as well as stored customer profiles ensure that the client gets the reason based service he or she needs, not intrusive advertising.

A client can make reservations as well as confirm, change, and cancel them using many kinds of communication means, including but not limited to the Internet, e-mail, and mobile terminals. The client can also synchronize a calendar provided by the mediator or a service provider with a calendar in a terminal device using mediator's synchronization functions.

A service provider can remind clients to make reservations on a regular basis and thus increase customer loyalty. A mediator can help service providers to bring their booking systems together to provide more comprehensive services without extending their businesses unnecessarily. Because of internationalization, the mediator is able to support for example many languages, time zones, currencies, and data formats.

The system, including at least a dialogue, a mediator, a service provider, and a service provider booking system, can be on one of the following levels:

1. There is a predetermined set of dialogues in the system. Their content and the possible choices are set in advance. For example, if a client books a flight, a dialogue always offers certain other bookings. Client's prior actions are not taken into consideration. 2. There is an unlimited number of dynamic or “intelligent” dialogues that are based on, for instance, a profile that a client has created himself or herself, usage history records, and client's location. Simple logic supports decisions. It is a low-level expert system. 3. The system is able to make decisions by itself and to support client's decision making. On this level, a dialogue may include a high-level expert system. It can act as an agent and negotiate with several service providers to get the best offer without client's direct involvement.

In one preferred embodiment of the method, a client books a service from a service provider. The booking may be carried out using a terminal that is connected to the mediator service. First, the client connects to the mediator service using a dialogue. The client inputs reservation inquiry to the dialogue that sends the inquiry to the mediator. The mediator inquires possible reservations from service provider's information system using concepts and terminology that those services are able to interpret. The inquiry is based on client's preferences. The client discloses some preferences that are related to the specific booking when he or she inputs reservation inquiry to the dialogue. In addition, the dialogue and the mediator service may have stored client's general preferences and use them so that the client do not need to input all the preferences each time.

Managing the inquiry and bookings is based on sophisticated state models. Each booking involves several phases that are described by states that track its status through its life cycle. For example, when the mediator has inquired about a reservation from a service provider, the corresponding entry in each system has a state that the booking is pending but not confirmed. If the systems do not have common understanding what a certain state means, the mediator translates them. A preferred booking process including the phases and states is described in Example 1.

In addition to inquiring reservations from the service provider, the mediator is able to synchronize bookings in several service providers' systems. The synchronization is based on rules specified in the mediator service. For example, a rule can be that “if a client inquires booking for an airline ticket, inquire also bookings for taxis to the airport.” Therefore, an inquiry from the client may be multiplied in the mediator service resulting a number of inquiries. The service providers answer to the mediator if they are able to provide requested service and they may add some additional information, like on seats or timing. The mediator combines gathered information and sends it to the dialogue that shows a simple list of options to the client. For example, the dialogue may show three options for a flight and ask if the client also wants to reserve a taxi that is actually already tentatively booked by the mediator. The client makes his or her decision by choosing the options from the simple list of alternatives. The dialogue sends information on client's choice to the mediator that confirms the bookings in accordance with client's choices and cancels the unnecessary reservations.

FIG. 4 shows a sequence diagram of an inquiry CINQ1 originated by a client using a dialogue DINQ1 sent to the mediator. The mediator initiates the inquiry MINQ1 which corresponds to CINQ1 and DINQ1 to booking system 1 a service provider booking system. Ultimately an answer DANS1 gets back to the client offering a choice which is responded to with a selection CSEL1 resulting in a booking by the client on booking system 1. The mediator recognizes the potential need for a complementary service from booking service 2 and initiates an inquiry, MINQ2, to booking system 2, which ultimately results in a proposal including several choices, DANS2, returned to the client from which a selection, CSEL2, is made, resulting in a complementary booking on booking system 2.

The bookings can be done in other means as well, for instance, by calling the service provider with a telephone or by visiting on site the service provider's office. In that case the service provider may inform the mediator about client's bookings so that the mediator can inform the client on other options. For example, a dentist could tell the mediator that the client has booked an appointment so that the mediator may offer to book a taxi also.

Also, it is possible to add a reminder to the mediator service so that the mediator asks at certain time if the client wants to make a new booking. For instance, the mediator can send a notice to the client that it has been a year since the client last had an appointment with his or her dentist and ask if the client wants to make a new appointment. This notice can already include a few options for the appointment. The mediator has checked the client's calendar if he or she has allowed that so that the given options are convenient for the client. The dialogue shows the options in a simple and handy way. The client needs only to choose which option is the best for him or her or whether he or she wants to get new options or postpone the booking. FIG. 5 is a time sequence chart for such a situation where the original inquiry, MINQ1, was initiated by the mediator.

Example 1 A Preferred Booking System

A preferred booking system according to the invention is described below in terms of a system named BookIt.

BookIT is designed to interface between service provider booking systems and other parties over a network such as the Internet, and to end user clients equipped with mobile phones capable of receiving text messages. The former is preferably accomplished with a generic XML interface. BookIT supports vCard and vCalendar standards since they are used by all major booking and calendar systems.

BookIT communicates with mobile phone users using Short Message Service (SMS) via an SMS Gateway for asynchronous communication. BookIT uses the novel Dynamic Dialogue Matrix (DDM) for secure transfer and mapping of the SMS messages. The DDM is described further below.

A clear distinction needs to be made between a service provider booking process and BookIT Process. The former covers the standard booking only with time and resource reservation. The latter consists of booking, work, and financing. Both processes end to the same point. The BookIT Process consists of seven phases as follows:

Phases (Status Handling)

The phases make a bond (rubber band) between the resources. In each of the BookIT Process' phases the data related to the booking will be amended to reflect the needs of the phase in question. For the statuses and values please see the underneath table.

The phases are described in more detail in the following discussion.

1. Filing

Filing means initialization of a BookIT Process and a booking process. As a result of the initialization an entry is inserted in the database w/basic information. It will not appear in a calendar since there is no scheduling information. It can be displayed in a separate task list of the owner as an open task.

2. Requesting

In the Requesting phase a booking request is sent to the resources required for the previously filed task. Since there is no scheduling, which in most cases will be essential, this phase may be executed together with the Scheduling phase.

3. Scheduling

Schedule is given to the owner and the resources. As a part and a result of the Scheduling the following data is needed:

a suggested start-time (ISO time-stamp w/time zone)

b suggested start-location (coordinates)

c suggested end-time (ISO time-stamp w/time zone)

d suggested end-location (coordinates)

4. Confirming

Time and location as it is accepted by the resources that have accepted. Data related to this phase:

a accepted start-time (ISO time-stamp w/time zone)

b accepted start-location (coordinates)

c accepted end-time (ISO time-stamp w/time zone)

d accepted end-location (coordinates)

By default the data is copied from the Planning phase.

In practice, if planned time is not needed, the same data structures can be used for this and status indicates the actual meaning of the data.

5. Working

The resources perform the booked task. Data related to this phase consists of different attributes and their values, which are related to the actual task. In addition, following static structures are needed:

a actual start-time (ISO time-stamp w/time zone)

b actual start-location (coordinates)

c actual end-time (ISO time-stamp w/time zone)

d actual end-location (coordinates)

e products used, extras, mileage, . . .

By default the data is copied from the Confirming phase.

6. Accounting

At this point all data stored in the data structures on previous phases is analyzed and processed for invoicing purposes.

Data related to this phase: Accounting data. To be defined separately.

7. Completing

The task has been completed. From the whole BookIT process point of view it is irrelevant whether the task succeeded or not. It is relevant to the Accounting phase, in which the financial actions to the organizer are handled. In this phase, housekeeping (database contents: temporary files, . . . ) is made in order to complete the BookIT Process.

The following table shows data available in each phase. Booking phase is in italics.

Filing X X Requesting X X X Scheduling X X X X Confirming X X X X X Working X X X X X X Accounting X X X X X X Completing X X X X X X X Phase/Data Identifying Resources Suggested Accepted Task's Accounting Closing time time work related Phase Statuses, Values, and Transitions

The following table describes the phases, their statuses, and values along with transition to next logical phase based on the values gotten. In addition, corresponding vCalendar statuses are shown when applicable.

Phase Satus Next Phase vEvent vTodo Filing Requesting Requesting Scheduling Sent Sent Scheduling Pending Confirming Needs Action Needs Action Scheduling Scheduled Confirming Needs Action Needs Action Scheduling Re-scheduled Confirming Needs Action Needs Action Confirming Accepted Working Confirmed Accepted Confirming Declined Accounting Declined Declined Confirming Tentative Accounting Tentative Confirming Delegated Requesting Delegated Delegated Confirming Re Scheduling Accounting or requested Scheduling Confirming InProgress Working Working InProgress Working Working Delayed Working Working Started Working Working n % ready Working Working Ready Accounting Accounting Completing Completing <Copied from n/a phase before Accounting>

Internal phases Paused, Re-started, and Canceled act as follows for all relevant phases at any point:

<Phase y> Paused <Status x> <Phase y> Re-started <Status x> <Phase y> Cancelled Accounting

FIG. 7 shows the work flow transitions from phase to phase. For conditions, see the table above. Also, please note that Canceled Status always leads to accounting.

Confirming the (Whole) Reservation

In order for the whole Reservation to be successful, all resources, which accepted the reservation, need to have the same scheduling. In addition, there will resources in different roles and data related to the working phase may vary even greatly.

The different statuses of the whole reservation are:

a “NoReplies” (0) for “No-one hasn't replied to the request made by the organizer”

b “NoDeclines” (1) for “Not all invitees have replied yet. The ones who have replied have accepted”

c “AllAccepts” (2) for “all invitees have confirmed”

d “SomeDeclines” (3) for “Some of the invitees have declined”

e “AllDeclines” (4) for “All of the invitees have declined”.

The following decision table helps in evaluating the status of the whole booking. “Maybe” means that this condition only does not incontestably specify true or false result.

Confirmations No one No one Some All No one Some All Booking Status answered accepted accepted accepted declined declined declined NoReplies True Maybe Maybe NoDeclines True Maybe Maybe True True NoAccepts True True Maybe Maybe True AllAccepts True True Maybe SomeAccepts True Maybe Maybe Maybe AllDeclines Maybe True SomeDeclines Maybe Maybe True Maybe

Based on the information and decision table above the organizer/application has to make the decision of what to do with the reservation. That can be an automatic decision made by the system based on pre-set rules or made by the organizer manually.

FIG. 6 shows an example of the dynamic dialog matrix applied to a query and reply according to the invention. An application sends a service request to a user to a mediator B. The mediator B picks up random B address from a group of available B addresses wherein it can receive responses from the user. After defining the B address, the mediator B sends a query to user A, wherein the query may consist of a list of choices from which the user A may select the reply. The user A receives the query in his/her terminal and sends a reply to that query to the B address. The mediator B receives the user's reply in the B address. After receiving the reply from the user A, the mediator B processes the reply. First the mediator B validates the A address (which is the user's address). In case the A address does not correspond to the A address whereto the message was sent, the mediator B may inform the application that no response was received. In case the A address corresponds to A address whereto the mediator B has sent a query to, the mediator B verifies the B address (the reply address into which the reply was received). Correspondingly, in case the B address is not a valid B address for the user, the mediator B may inform the application that no response was received. In case also the B address corresponds to the B address that the message was sent from, the mediator B matches the reply C to the list of available choices for that message. If the reply does not correspond to the available list of choices, the mediator B may send an error information to the application, or send a new query to the user A. If the reply corresponds to the available list of choices that was sent to the user, the mediator B sends a return service response to the application.

Preferably, the system with reference to FIG. 6 has a plurality B subscriber numbers (telephone numbers), wherefrom the mediator B may select a subscriber number where the message to the user A is sent. Further, the user A preferably has a mobile telephone, having a mobile subscriber number, whereto the message is sent, and wherefrom the user A may respond to the query. The messages to and from the mediator B is sent over the telecommunication network.

One major problem solved by the invention is the challenge of managing client replies, when a client has been given a number of questions and the client is using SMS text messages or similar technology in which a reply does not automatically include an explicit reference to the inquiry. The invention solves this problem using dynamic dialog matrices. An inquiry always includes some kind of receiver's address or identification. In the SMS text message case that is so called B subscriber's number. On the other hand, sender's A subscribers number or Calling Line Identity (CLI), or similar identification is also attached to each text message. Therefore the client or B subscriber is usually easily able to answer a message using mobile device's answer or reply function. If a mediator service that sends inquiries to a client, uses different A subscriber numbers in different inquires, it is possible to differentiate between answers based on which number the client is sending replies to. For example, if a mediator sends a client an inquiry “Do you need a taxi also?” using A subscriber number A1 and then inquiries “Do you need a hotel room?” from A subscriber number A2, client's reply to the first question goes to number A1 and the second answer goes to number A2. Using a dialog matrix, a mediator keeps track on inquires and answers. In the matrix, there is a column for each client and a row for each A subscriber number the mediator is using. Obviously, there could be a row for each client and correspondingly a column for each A subscriber number as well. After sending an inquiry from a certain A subscriber number to a client, the status and the reply is stored in the corresponding shell of the matrix. As a result, the mediator is able to find out whether the client has replied to a certain inquiry and what the answer was. Also, it is possible to use the matrix to collect information about clients' behavior and use it for example for marketing purposes. A mediator needs only a limited number of A subscriber numbers. A dialog matrix can also be used to find out which A subscriber numbers can be used when the next inquiry to a certain client is sent.

The use of the Dynamic Dialog Matrix as described above is illustrated in FIG. 7.

The Dynamic Dialog Matrix is also a powerful but very simple security measure for authenticating a mobile phone user who has only the capability of sending and receiving messages. The problem is for a service to confirm a sender's identity. One way to try to identify the user is to check the sender's address. Normally SMS, e-mail, and other alike messages have the sender's address attached. That address can be for example the sender's A-subscriber's number or Calling Line Identity (CLI), or e-mail address or IP address. However, it is quite easy to falsify a sender address. From the service provider's perspective, the downlink from a service provider to a user is usually relatively reliable and it is hard for others to capture or change messages, but the uplink from a user to a service provider is much more vulnerable and it is not too difficult to give a wrong sender's address. A well-known solution to the above problem is to use encryption technologies to secure the communications, public-key infrastructures (PKI) being good examples. For instance, a user device can be equipped with a microchip, a secure SIM card in GSM devices for example, to encrypt messages using the user's private key. Then the service provider can be sure that the message is from the user, if it can be decrypted using the user's public key. However, this solution requires special devices that are not very common, inexpensive, or standardized so far. Relying on such a solution restricts the number of potential users significantly.

Using the DDM provides a novel solution. When the service sends a request to the mobile phone user, each request contains a different, preferably randomly chosen, reply number. Thus an acceptable answer is only the one that is sent to the correct reply address.

An example is for authenticating a user who is making a purchase, e.g. purchasing a software product. The user first initiates a purchase request to the company/service, e.g. directly in the software program, via an internet website or via a mobile device. The company/service then knows the user name and possible other identification information and sends a request to a credit card company to request a payment. The credit card company then sends a request to a mediator to authenticate the purchase. The mediator knows the user and the user's mobile number and sends a message, e.g. SMS or MMS, to the user's known phone number. An example of a message could be:

Dear Mr. Salonen, your credit card was used to purchase Office on 27 Mar. 2010 for 299 euros. Please reply

y- to accept the payment on VISA xxxx xxxx xx 123

n- to reject the payment or

f- to report a fraud on your credit card.

By responding to the message from the known user's mobile number with an acceptable response allows the mediator to respond to the credit card company if the user authorizes the purchase or not. Thereafter, the credit card company may authorize the payment and inform the company/service. Additionally, if the mediator sends the message from a randomly chosen reply number as discussed above, there is an added layer of authentication. Because it is possible for a fraudulent user to determine a credit card holder's mobile number and fake a message from said number, it would be extremely improbable for them to know which reply number the authentication message would originate from. The above may also be used, for example, with money transfers between a user's bank and the company/service.

An additional element of security can be achieved using semantic analysis. For example, if the user is asked to tell how many items are ordered, and the answer is “yes”, then apparently the user did not know what the question was and the message was not an answer for the enquiry.

Such a system can also provide a level of security for the user. The mediator can authenticate the company/service, by any acceptable method, and only send authentication messages once the company/service has been authenticated. Then, if the user does not provide their mobile number when providing their identification information, when they get an authentication message, even from a number they do not recognize, they will know that the mediator has authenticated the company/service.

While the present example has been explained in terms of the mediator sending the message, the message could be sent by a secondary entity at the request of the mediator. For example, when the mediator receives a request to authenticate a transaction, the mediator can then provide the user's bank with the necessary transaction details and request that the bank send the necessary authentication method. Another example would be if the mediator sends a request to the bank for some of the user's identity information, e.g. mobile number, so that it can proceed with sending the actual request itself or through a tertiary service provider which handles the actual message sending.

Additionally, though the present example has been described with the transaction being the purchase of a product and authentication of the user for payment, the same system and similar method can be used for other transactions, such as the authentication of the purchased product.

The use of a Dynamic Dialogue Matrix allows for authentication and verification of products, services and transactions based on a plurality of combinations of data. Based on as little as two pieces of information from the DDM an entity can be verified. Based on more pieces of information from the DDM, a higher degree of verification can be achieved.

A DDM which is being used for verification purposes can contain, or have access to, multiple of some or all of the following: reply addresses used for sending messages, reply addresses for which messages are received, user addresses, questions, acceptable answers for questions, order of receiving answers and verification information (e.g. product keys, ID codes). A key to the DDM is that it allows verification between a company/service and a user through a mediator (and possibly another party) by matching information that each entity knows and the others should not know. Several examples are as follows:

If a user downloads a piece of software from the internet they want to know that the software is legitimate, i.e. not pirated or hacked and software developers want to make sure that users are paying to activate their programs. Therefore, prior to use the user is requested to enter a product key. The user sends a message, e.g. SMS, to a number with a product ID code. If the ID code is valid and has not been previously registered then the user receives a message with the product key. Therefore, the DDM matches the user entered product ID code with an indicator if it has been registered to verify if a product key should be issued. A similar process could work in conjunction with the payment process described above. Once the purchase of the software is authenticated as described above then an additional message can be sent to the user with the applicable product key.

A similar method and system can be used to verify the legitimacy of virtually any product, such as medicine or trademarked products. If the product has a code printed on the packaging and a known number associated with the products manufacturer or verification then a consumer can send a message to the known number with the product code to receive an indication if the code is valid and if it has been previously checked. Benefits to this system are that if pirated products do not have a code printed on the product or have an invalid code then the user will know right away. Additionally, if multiple users check the same code then the product manufacturer or verifier can check in to if the code has been reproduced by a manufacture of a pirated product. A further benefit to the system is that the product manufacturer can immediately send an inquiry back to the user if the product is determined to be pirated or suspected of piracy. An inquiry may be to ask where/when the product was purchased, what the purchase price was and/or other information which can be used to identify the entity responsible for the piracy or distribution of pirated goods.

The process may also be such that the user sends a code to the known number to receive information if the product is authentic or a pirate product. Thereafter, the manufacturer requests a further code or alike information from the user. When using two pieces of information (and possibly another sender identity than whereto the user sent the first message) to authenticate the product, the level of security is increased.

Example 2—Use of the Dynamic Dialogue Matrix

This simple example deals with securing tickets on a morning flight tomorrow. The system sends a series of questions as SMS messages requiring a short response. Each message is earmarked so that its response can be identified so the messages need not necessarily be sent or replied to in a particular sequence unless logic so demands (for instance, if the answer to one question affects the content of the next question).

A user whose phone number is ID=0418 979 813 has requested the ticket. The system sends the following requests as individual SMS messages:

Please choose one of the following departure times:

6:00 a.m., answer A

7:30 a.m., answer B

8:15 a.m., answer C.

If none of these is OK, answer D.

Sender: +358440844 027

Please choose ticket class:

First class, answer A

Business class, answer B

Economy class, answer C

Cheapest available, answer D

Sender: +358440844 011

Please choose:

Window seat, answer A

Aisle seat, answer C

Sender: +358440844 034

Please select the meal:

Vegetarian, answer A

Beef answer B

Chicken, answer C

Sender: +358440844 003

The answers received from the customer to the preceding questions and several others were

‘A’ to question with ref. no +358 440 844 027

‘D’ to question with ref. no +358 440 844 011

‘A’ to question with ref. no +358 440 844 034

‘B’ to question with ref. no +358 440 844 003

‘D’ to question with ref. no +358 440 859 751

‘A’ to question with ref. no +358 440 844 277

‘C’ to question with ref. no +358 440 841 368

From this, the service provider can find out that the customer chose:

the first morning flight (=A),

cheapest available ticket (=D),

window seat (=A),

beef for meal (=B),

and etc.

It is important to note with the matrix the customer can answer the questions in any order, and can even fail to answer some questions. If these are relevant, the system can urge for an answer. If not, the system can proceed without this information.

The above responses are shown on FIG. 8 as a three dimensional matrix with customer numbers plotted on the X-axis, reply numbers are plotted on the Y-axis and answers plotted on the Z-axis. Our user with phone number 0418 979 813 is the left most user along the X-axis. The answers are plotted along the Z-axis corresponding to the reply numbers on the Y-axis.

Additional security can be achieved using semantic analysis. In the matrix shells, there can be information about the inquiry and what kinds of answers are acceptable. If an answer does not meet the criteria, it is rejected. For example, if the service provider asks the user to tell how many items are ordered, and the user answers “yes”, then apparently the user did not know what the question was and the message was not an answer for the inquiry.

It is also possible that the service provider is actually a mediator and the “real” service provider is somewhere else. In that case, only the mediator needs to have the matrix-based system and the actual service provider communicates with the mediator using either the mediator's matrix-system or other secure means like a crypto-channel. For example, a car sharing system could be implemented in the following way: cars are located randomly around a city. When a user needs a car, he or she sends a message to a mediator to ask where the nearest car is. The mediator sends a message telling the car's location. That reply comes from a random address y′. When the user reaches the car, he or she sends a message to y′ telling that the rental period begins and asking the mediator to remotely release the car's locks. This message is relatively reliable, because it is sent to the address that the user only knows. Therefore it constitutes a valid reason to release the locks and start billing. The communication between mediator and the car, on the other hand, is invisible to the user and outsiders. The car can be equipped with special devices and therefore remote commands to release the locks etc. can be encrypted. Or, the communication between the car and the mediator could also be implemented using matrices. In either case, the mediator operates as a “firewall” between the user and the car disabling outsiders from unauthorized usage.

Similar series of messages can be used in conjunction with the authentication and verification as described above. For instance, if a software developer offers a 30-day trial version of their software they can require that a user enters a mobile number to activate the software. Then, based on a triggering event, a mediator can send a desired message to the user. Examples of triggering events are that the developer asks whether the installation succeeded, that the trial period is ending or has ended, that the user has not used the software for a certain period of time or the user has recently used the software. One example would be if the triggering event was that the trial period was ending the mediator could send a series of messages as follows:

You have downloaded a trial version of our software and the trial period has ended.

Please reply if you

A: did not have time to adequately test the software and would like more time,

B: would like to purchase a full version of the software or

C: would not like to continue using the software.

By responding “A” to the message the user could receive a code to enter in to the software which would give the user an additional period of time for trial. Because the software is linked to the user's mobile number from the initial activation, the mediator will know when this period runs out that it has already been extended and may not offer that option next time the trial period ends. Additionally, if someone else tried to send “A” to the number from their own mobile number the mediator would know that they had not activated any software and would know not to send any extension codes. If the user would like to purchase a full version then the user could respond with “B” and then pay and be authenticated through their mobile device as described above. If the user replies with “C” then a series of messages constituting a survey could be sent in order to help the software developer determine why the user did not want to purchase their product. Furthermore, in return for, or in response to certain answers, the mediator could send a code as a reward to the user. Again, since the mobile number of the user is tied to the software the mediator prevents other people with other mobile numbers to send a message “C” to the software developer's number in order to receive a reward. Further, other user's do not know from which number the software developer has sent the message.

An embodiment of the present invention is a method for authenticating a user having a known address comprising the steps of; sending a first message to the known address from a first reply address, receiving a reply to the first message from the known address to the first reply address, sending a second message to the known address from a second reply address, receiving a reply to the second message from the known address to the second reply address, authenticating the user based on the received replies from the known address, and wherein the first and second reply addresses are selected from a plurality of available reply addresses. Additionally, the method in accordance with the embodiment may further comprise the steps of; receiving a request to authenticate a user at a known address prior to sending the first message, and sending the authentication determination to the party that requested the authentication. A method in accordance with the embodiments may also include wherein one or more additional messages are sent to the known address. A method in accordance with the embodiments may also include wherein once a reply address is selected from the plurality of available reply addresses it becomes unavailable for future selection as a reply address to the known address. A method in accordance with the embodiments may also include wherein each reply address is randomly selected from the plurality of available reply addresses. A method in accordance with the embodiments may also include wherein at least one of the messages includes an authentication question and at least one of the subsequent replies includes an answer to said authentication question. A method in accordance with the embodiments may also include wherein authenticating the user includes determining an authentication level based on the number of the plurality of available reply addresses and/or the replies to at least one of the messages. A method in accordance with the embodiments may also include wherein the authentication is additionally based on the time between sending a message and receiving the corresponding reply. A method in accordance with the embodiments may also include wherein the known address and at least a portion of the plurality of reply addresses are telephone or mobile phone numbers.

Another embodiment of the present invention is a method of software activation which comprises associating each software distribution with a unique activation code, providing a user who downloads the software with said activation code, the activation code being sent to an identifiable electronic device, retrieving information related to the identifiable electronic device and associating the activation code with the identifiable electronic device to obtain a fingerprint of said activation, storing said fingerprint including the activation code and information of the identifiable electronic device and authorizing subsequent activation of the software only to said user with said identifiable electronic device information.

Another embodiment of the present invention is a system for authenticating a user having a known address comprising; a plurality of available reply addresses a means for sending messages having one of the plurality of reply addresses a means for receiving replies to the reply addresses, and a controller configured to send a first message to the known address from a first reply address, send a second message to the known address from a second reply address and to authenticating the user based on received replies from the known address to the reply addresses.

Although the present invention has been described in considerable detail with reference to certain preferred versions thereof, other versions are possible. For example, the user's known address can be an email address or mobile telephone address as described above or it can be an online account name, such as a log-in ID. Many online accounts have 2-way and multi-way messaging features where messages are addressed to the online account name or a derivative thereof. In such instances, the present invention can be implemented with the messaging system of online account and the user's online account name. Therefore the spirit and scope of the appended claims should not be limited to the preferred versions herein. 

The invention claimed is:
 1. A transaction processing system for processing confirmation of a transaction for a user via a mobile phone of the user, the transaction processing system comprising: a mediator server that receives and sends transaction confirmation information for a transaction to be made between a user and a network server based on the received and sent transaction confirmation information, wherein the transaction confirmation information includes information sent from the network server to the mediator server, information sent from the mobile phone of the user to the mediator server, information sent from the mediator server to the network server and information sent from the mediator server to the mobile phone of the user, wherein the transaction confirmation information includes a mediator server address and a user address; a dialogue on the mobile phone of the user, wherein the dialogue enables the user to enter transaction confirmation information into the transaction processing system for sending to the mediator server in response to a query sent from the mediator server, wherein the mediator server analyzes the received transaction confirmation information from the dialogue on the mobile phone of the user to generate and transmit transaction confirmation information for the user to be sent to the network server confirming the transaction, wherein the mediator server performs analysis of the mediator server address and the user address in the transaction confirmation information received at the mobile phone of the user, wherein the dialogue is authenticated based on the mediator server address and the user address by performing an analysis of the mediator server address and the user address in the transaction confirmation information against a predefined mediator server address and user address, and wherein the dialogue supports decision making by the user by presenting the user with possible choices for inputting information using the dialogue in response to transaction confirmation information received from the mediator server at the mobile phone of the user.
 2. The transaction confirmation system of claim 1, wherein the dialogue includes possible choices for inputting transaction confirmation information.
 3. The transaction confirmation system of claim 1, wherein the transaction confirmation information pertains to a transaction for delivery of a service to the user by the network server.
 4. The transaction confirmation system of claim 1, wherein the dialogue is based on the user's usage history information.
 5. The transaction confirmation system of claim 1, wherein the generation and transmission of the transaction confirmation information by the mediator server is based on profile information of the user.
 6. The transaction confirmation system of claim 5, wherein the user profile information is stored in the mediator server.
 7. The transaction confirmation system of claim 1, wherein the dialogue is based on the user's location.
 8. The transaction confirmation system of claim 1, wherein the transaction confirmation information relates to an appointment for the user.
 9. The transaction confirmation system of claim 1, wherein the transaction confirmation information is exchanged with the mediator server via text messaging, Short Message Service, Multimedia Message Service, electronic-mail, Internet mail, voice mail, Web browser, telephony application, call center, video conference, Personal Information Manager, Personal Data Assistant or smart card.
 10. The transaction confirmation system of claim 1, wherein the dialogue is configured to enable the user to send transaction confirmation information including a transaction request for the transaction to the network server through the dialogue on the user's mobile device.
 11. The transaction confirmation system of claim 10, wherein the transaction request for the transaction includes transaction confirmation information that includes a name of the user.
 12. The transaction confirmation system of claim 11, wherein, in response to the initiation of the transaction request, the mediator server receives transaction confirmation information including a request to authenticate the transaction, wherein the request to authenticate the transaction was generated by a financial company that received a request for the transaction from the network server that received the transaction request for the transaction from the user's mobile device via the dialogue.
 13. The transaction confirmation system of claim 12, wherein, in response to receiving the request to authenticate the transaction from the financial company, the mediator server sends transaction information including a request to process the transaction corresponding to the transaction request sent from the dialogue on the mobile phone of the user.
 14. The transaction confirmation system of claim 13, wherein the financial company is one of a credit card company, an online payment provider or a bank.
 15. The transaction confirmation system of claim 13, wherein the transaction request includes the user's name, an identification of a user's financial account, an amount to be charged as a result of accepting transaction and at least one choice signal to be selected by the user to indicate acceptance or rejection of the transaction.
 16. The transaction confirmation system of claim 15, wherein, in response to receiving a user's response to the request to accept transaction, the mediator server performs semantic analysis on the received response content as part of authentication of the received response.
 17. The transaction confirmation system of claim 1, wherein the dialogue includes an expert system that supports decision making by the user by presenting the user with possible choices for inputting information using the dialogue in response to transaction confirmation information received from the mediator server at the mobile phone of the user.
 18. The transaction confirmation system of claim 1, wherein the mediator server mediates a plurality of transactions for the user authenticated via the mobile phone of the user, each transaction involving a respective electronic transaction.
 19. The transaction confirmation system of claim 1, wherein the mediator server mediates at least one transaction between the user and a network server by transmitting identifier data other than financial data for the user over at least one network such that the transmitted identifier data enables identification by the mediator server of financial data for the user to facilitate processing of at least one electronic transaction.
 20. The transaction confirmation system of claim 1, wherein the possible choices presented to the user are selectable by the user to authorize the transaction in which transaction is provided to the network server in exchange for a service.
 21. A method for processing confirmation of a transaction for a user via a mobile phone of the user, the method comprising: receiving and sending, at a mediator server, transaction confirmation information for a transaction to be made between a user and a network server based on the received and sent transaction confirmation information, wherein the transaction confirmation information includes information sent from the network server to the mediator server, information sent from the mobile phone of the user to the mediator server, information sent from the mediator server to the network server and information sent from the mediator server to the mobile phone of the user, wherein the transaction confirmation information includes a mediator server address and a user address; enabling, using a dialogue on the mobile phone of the user, the user to enter transaction confirmation information into the transaction processing system for sending to the mediator server in response to a query sent from the mediator server; analyzing, at the mediator server, the received transaction confirmation information from the dialogue on the mobile phone of the user; generating transaction confirmation information based on the analysis of the received transaction confirmation for the user; and transmitting the transaction confirmation information for the user to the network server authorizing the transaction, wherein the mediator server performs analysis of the mediator server address and the user address in the transaction confirmation information received at the mobile phone of the user, wherein the dialogue is authenticated based on the mediator server address and the user address by performing an analysis of the mediator server address and the user address in the transaction confirmation information against a predefined mediator server address and user address, and wherein the dialogue supports decision making by the user by presenting the user with possible choices for inputting information using the dialogue in response to transaction confirmation information received from the mediator server at the mobile phone of the user.
 22. The transaction confirmation processing method of claim 21, wherein the dialogue includes possible choices for inputting transaction confirmation information.
 23. The transaction confirmation processing method of claim 21, wherein the transaction confirmation information pertains to delivery of a service to the user by the network server.
 24. The transaction confirmation processing method of claim 21, wherein the dialogue is based on the user's usage history information.
 25. The transaction confirmation processing method of claim 21, wherein the generation and transmission of the transaction confirmation information by the mediator server is based on profile information of the user.
 26. The transaction confirmation processing method of claim 25, wherein the user profile information is stored in the mediator server.
 27. The transaction confirmation processing method of claim 21, wherein the dialogue is based on the user's location.
 28. The transaction confirmation processing method of claim 21, wherein the transaction confirmation information relates to an appointment for the user.
 29. The transaction confirmation processing method of claim 21, wherein the transaction confirmation information is exchanged with the mediator server via text messaging, Short Message Service, Multimedia Message Service, electronic-mail, Internet mail, voice mail, Web browser, telephony application, call center, video conference, Personal Information Manager, Personal Data Assistant or smart card.
 30. The transaction confirmation processing method of claim 21, wherein the dialogue is configured to enable the user to send transaction confirmation information including a transaction request for the transaction to the network server through the dialogue on the user's mobile device.
 31. The transaction confirmation processing method of claim 30, wherein the transaction request includes transaction confirmation information that includes a name of the user.
 32. The transaction confirmation processing method of claim 30, wherein, in response to the initiation of the transaction request, the mediator server receives transaction confirmation information including a request to authenticate the transaction, wherein the request to authenticate the transaction was generated by a financial company that received a request for transaction for the transaction from the network server that received the transaction request for the transaction from the user's mobile device via the dialogue.
 33. The transaction confirmation processing method of claim 32, wherein, in response to receiving the request to authenticate the transaction from the financial company, the mediator server sends transaction information including a request to accept transaction corresponding to the transaction request sent from the dialogue on the mobile phone of the user.
 34. The transaction confirmation processing method of claim 33, wherein the financial company is one of a credit card company, an online transaction provider or a bank.
 35. The transaction confirmation processing method of claim 33, wherein the request to accept transaction includes the user's name, an identification of a user's financial account, an amount to be charged as a result of accepting transaction and at least one choice signal to be selected by the user to indicate acceptance or rejection of the transaction.
 36. The transaction confirmation processing method of claim 35, wherein in response to receiving a user's response to the request to accept transaction, the mediator server performs semantic analysis on the received response content as part of authentication of the received response.
 37. The transaction confirmation processing method of claim 21, wherein the dialogue includes an expert system that supports decision making by the user by presenting the user with possible choices for inputting information using the dialogue in response to transaction confirmation information received from the mediator server at the mobile phone of the user.
 38. The transaction confirmation processing method of claim 21, wherein the mediator server mediates a plurality of transactions for the user authenticated via the mobile phone of the user, each transaction involving a respective electronic transaction.
 39. The transaction confirmation processing method of claim 21, wherein the mediator server mediates at least one transaction between the user and a network server by transmitting identifier data other than financial data for the user over at least one network such that the transmitted identifier data enables identification by the mediator server of financial data for the user to facilitate processing of at least one electronic transaction.
 40. The transaction confirmation processing method of claim 21, wherein the possible choices presented to the user are selectable by the user to authorize the transaction in which transaction is provided to at least one network server in exchange for a service. 